Make sure we don't call back into GtkEntryBuffer
authorEmmanuele Bassi <ebassi@gnome.org>
Wed, 9 Sep 2020 10:29:16 +0000 (11:29 +0100)
committerEmmanuele Bassi <ebassi@gnome.org>
Wed, 9 Sep 2020 10:29:16 +0000 (11:29 +0100)
commitf4b410daa751aa85997cd530131b81e8d7e63ff7
tree2a35508b3dd8ba6e17db4b1c5584e0e5b8c9ac07
parentb3d3d81c8260eb83fcf61fa0e40b830faf17df8d
Make sure we don't call back into GtkEntryBuffer

After commit 7e77afe94c14365d538c958d23c1e3e074530415 moved the deletion
of text into the signal handler, in order to make undo work, we need to
override the GtkEntryBuffer::deleted-text class closure when subclassing
GtkEntryBuffer, as well as overriding GtkEntryBufferClass.delete_text,
otherwise the default class closure will be invoked, and will try to
delete an empty buffer.

Fixes: #3140
gtk/gtkpasswordentrybuffer.c